MRS V3.4 Protocol Reference V2
This chapter describes the OSI/DECnet V configuring and monitoring commands
and includes the following sections:
For information on how to access the OSI configuration
environment, refer to "Getting Started (Introduction to the User
Interface)" in the Software User's Guide.
This section summarizes and then explains the OSI configuration
commands. The OSI configuration commands enable you to create or modify
an OSI configuration. Enter all the OSI configuration commands
following the OSI Config> prompt. Defaults for any
command and its parameters are enclosed in brackets immediately following the
prompt.
The configuring commands manipulate the permanent OSI database
(SRAM).
Table 107. OSI Configuration Commands Summary
Command
| Function
|
? (Help)
| Displays all the commands available for this command level or lists the
options for specific commands (if available). See "Getting Help".
|
Add
| Adds areas this node supports; receive passwords for
authentication purposes; prefix addresses for other domains; and
aliases
|
Change
| Modifies some parameters set up with the add
command.
|
Clear
| Clears a receive password, transmit password, or SRAM
|
Delete
| Deletes areas, PVCs, prefix-addresses, adjacencies, aliases,
subnets, and X.25 routing circuit parameters.
|
Disable
| Disables a subnet, the OSI protocol, or an X.25 routing
circuit.
|
Enable
| Enables a subnet, the OSI protocol, or an X.25 routing
circuit.
|
List
| Displays the current configuration of adjacencies, aliases,
passwords, pvcs, prefix-addresses, subnets, algorithm, phaseivpfx,
global information, or X.25 routing circuits.
|
Set
| Configures the properties associated with OSI parameters (switches,
globals, NETs, timers, subnets, transmit-password,
prefix-addresses, adjacencies, pvc, algorithm, and phaseivpfx)
|
Exit
| Returns you to the previous command level. See "Exiting a Lower Level Environment".
|
Use the add command to configure area and prefix addresses,
receive passwords, and address aliases.
Syntax:
- add
- alias
-
- area...
-
- filter...
-
- prefix-address
-
- receive-password
-
- routing-circuit...
-
- template...
- alias
- Adds an ASCII string that designates a particular area address or system
ID. The ASCII string can be a-z, A-Z, 0--9, a
few other characters including the hyphen ( - ), comma
( , ), and underscore ( _ ). Do not use escape
characters.
The offset indicates the position, in semi-octets (nibbles), where the
ASCII string begins within the address (aliases used for system IDs have an
offset of 1). The string must be the same size or longer than the
segment it is designating or you will receive an invalid segment
length message. The maximum allowable alias is 20 bytes.
Note: | When using an alias input, you must surround it with brackets. For
example: l1_update
47[newname]99999000012341234.
|
Example:
add alias
Alias [ ]:
Segment [ ]:
Offset [1]:
- Alias
- The character string you want to use
- Segment
- The NSAP segment that the alias is replacing
- Offset
- The location of the alias (in 4-bit, semi-octets) within the
NSAP. The offset is determined from the beginning (left) of the NSAP as
it is displayed on the terminal.
- area area-addr
- Adds additional area addresses (18-byte maximum) that the node
supports. An L1 node that supports other areas considers those
synonymous areas. One area address is the area portion of the
configured NET. If you try to add a duplicate area address, the router
will display an error message.
Example:
add area 47000580999999000012341234
Note: | When adding synonymous areas to an L1 node, use the set globals
command to configure the maximum number synonymous areas allowed for this
node. All routers within an area must use the same maximum number of
synonymous areas. Adjacencies can not be established if they are
different.
|
- filter filter-name routing-circuit-name calling-DTE call-UserData
priority
- Adds parameters upon which the router bases its acceptance of incoming
X.25 calls on an routing circuit, either a static incoming or
dynamically assigned (DA) circuit.
The filter-name is the name you give the filter. The
routing-circuit-name is the name of the routing circuit with which
the filter is associated.
The calling-DTE is the address of the calling router.
The local router checks the DTE address of an incoming call against a
prioritized list of filters for all circuits. A higher filter
priority in the list means that a connection to that filter's
calling DTE address is made first. It is recommended that you assign a
higher priority to filters for static circuits than for DA circuits.
This can prevent an incoming static call from being assigned a DA
circuit.
The call-UserData can have one of three values - osi,
dec, or user:
- For osi, the router automatically configures an ISO protocol
discriminator for the call data and requires the call to be from an OSI
node.
- For dec, the router expects the incoming calls to be from a
Digital Equipment Company router.
- For user, you are prompted for an additional entry of up to 16
octets. Enter text to constrain the acceptance of incoming
calls. The call-UserData field of the incoming call must
match the specified text.
Example:
add filter
Filter Name [ ]:
Routing Circuit Name [ ]:
DTE Address [ ]:
Call UserData (OSI/DEC/USER)]:
If you select user, and additional prompt appears for you to
enter user data, followed by a Priority prompt:
(max 16 octets) [ ]?
Priority (1-10) [5]?
- prefix-address
- Adds static routes to destinations outside the IS-IS domain.
This parameter prompts you for different information depending on the type of
subnet (X.25,
LAN, or FRL) that was configured using the set subnet
command.
Note: | If no Address Prefix is entered, the default prefix is assumed.
|
Example:
LAN Subnet:
add prefix-address
Interface Number [0]:
Address Prefix [ ]:
MAC Address [ ]:
Default Metric [20]:
Metric Type [Internal]:
State [ON]:
X.25 Subnet:
add prefix-address
Interface Number [0]:
Address Prefix [ ]:
Mapping Type[Manual]:
DTE Address[]:
Default Metric[20]:
Metric Type [Internal]:
State [ON]:
Frame Relay Subnet:
add prefix-address
Interface Number [0]:
Address Prefix [ ]:
DTE Address [ ]:
Default Metric [20]:
Metric Type [Internal]:
State [ON]:
Note: | If the subnet does not exist, you will receive the error message Subnet
does not exist - cannot define a reachable
address.
|
- Interface Number
- Defines the interface over which the address is reached
- Address Prefix
- Defines the NSAP prefix (20 bytes maximum).
- MAC Address
- Defines the destination MAC address. You must specify this address
if the interface corresponds to a LAN subnet. This prompt will only
appear if the interface is connected to a LAN subnet.
- Mapping Type
- Defines how the destination physical address is determined, manual or
X.121.
- If manual, the protocol will prompt for the DTE address.
- If X.121, the protocol will not prompt you for the DTE
address. The DTE address in this instance is extracted from the
NSAP.
- DTE Address
- Defines the destination DTE address. You must specify this address
if the interface is X.25 and the mapping type is manual. This
prompt only appears if the interface is configured for X.25 and the
mapping type is manual.
- Default Metric
- Defines the cost of the address.
- Metric Type
- Defines whether the metric cost is used for external (E) routing or
internal (I) routing.
- State
- When set to ON, this prefix-address is advertised to other L2
routers. When set to OFF, this is a non-functional
prefix-address.
- routing-circuit
- Adds a communications channel for X.25 switched virtual circuits
(SVCs) that the routing layer uses to send and receive data.
The routing circuit parameter is only applicable if you configure your
router as a DEC-type router. You can specify on of these types of
routing circuit:
- static-in
- static-out
- dynamically-assigned
A static-in circuit handles incoming X.25 calls. A call
filter (see add filter) specifies data the router uses to accept or
reject incoming calls on the circuit. A static-out circuit initiates
outgoing X.25 calls. The router uses a call template (see
add template) to make outgoing calls. A dynamically-assigned
circuit can have multiple SVCs running simultaneously. Unlike static
circuits, the router uses a dynamically-assigned circuit only when there is
traffic in or out of the router. It closes the dynamically-assigned
circuit upon expiration of an idle timer.
The add routing-circuit command prompts you for values for its
parameters.
Example:
add routing-circuit
Interface number [0]?
Circuit Name [ ]?
Circuit Type (STATIC/DA) [STATIC]?
Circuit Direction (OUT/IN) [OUT]?
If you select STATIC and OUT, the following
additional prompts appear:
Recall Timer (0-65535) [60]?
Max Call Attempts (0-255) [10]?
Initial Min Timer (1-65535) [55]?
Enable IS-IS [YES]?
Level 2 only [NO]?
External Domain [NO]?
Default Metric [20]?
ISIS Hello Timer [3]?
Enable DECnetV Link Initialization [YES]?
Modify Receive Verifier (YES/NO) [NO]?
Transmit Verifier (YES/NO) [NO]?
Explicit Receive Verification (TRUE/FALSE) [TRUE]?
If you select STATIC and IN, the following additional
prompts appear:
Initial Min Timer (1-65535) [55]?
Enable IS-IS [YES]?
Level 2 only [NO]?
External Domain [NO]?
Default Metric [20]?
ISIS Hello Timer [3]?
Enable DECnetV Link Initialization [YES]?
Modify Receive Verifier (YES/NO) [NO]?
Modify Transmit Verifier (YES/NO) [NO]?
Explicit Receive Verification (TRUE/FALSE) [TRUE]?
If you select DA for the circuit type, the following additional
prompts appear:
Recall Timer (0-65535) [60]?
Reserve Timer (1-65536) [600]?
Idle Timer (1-65536) [30]?
Max SVCs (1-65535) [1]?
- Interface Number
- Specifies the logical X.25 interface for this
routing-circuit.
- Circuit Name
- Sets up the alphanumeric name of this routing-circuit record.
- Circuit Type
- Specifies whether this routing circuit is either a STATIC circuit or a
DYNAMICALLY ALLOCATED circuit.
- Circuit Direction
- Specifies IN or OUT to determine whether the SVC of the static circuit
will be established with an incoming call request or an outgoing call
request. In both cases, the SVC is initially established upon operator
action, but the circuit is not fully enabled until both ends of the circuit
have initialized successfully.
- Recall Timer
- Defines the time in seconds that an out-static circuit or a DA circuit
must wait before attempting a new call request. This is a result of the
initial call request failing or a subsequent call having been cleared.
- Max Call Attempts
- If a call request fails, Max Call Attempts defines the maximum number of
subsequent call requests that are attempted by the out-static circuit before
no further attempts are made. At this point, a call failure is logged
and operator intervention is required to activate the out-static
circuit.
- Initial Min Timer
- Specifies the amount of time (in seconds) an out-static circuit waits for
a link to be initialized (reception of either an ESH or an ISH) after the call
request has been accepted. If the initial min timer expires before the
link has been fully initialized, the SVC is cleared and an event generated
that indicates initialization failure.
- Enable IS-IS
- Defines whether the IS-IS protocol is enabled on this
routing-circuit. When set to ON, the IS-IS protocol is enabled;
when set to OFF, the IS-IS protocol is not enabled.
- Level2 Only
- Specifies if this routing-circuit is used for Level2 routing only.
- External Domain
- Specifies whether the router transmits and receives messages to and from a
domain outside its IS-IS routing domain.
- Default Metric
- Defines the cost of this address.
- ISIS Hello Timer
- Defines the time interval between transmission of ISIS hellos.
- Enable DECnetV Link Initialization
- Defines whether DEC-style link initialization for this circuit is enabled
(YES) or not (NO).
- Modify Receive Verifier
- Specifies verification data to be checked against on receiving an XID when
verifying by circuit.
- Modify Transmit Verifier
- Specifies verification data to be included in the XID.
- Explicit Receive Verification
- Defines whether verification is by circuit or by system. TRUE
specifies verification by circuit, and FALSE specifies by system.
- Reserve Timer
- Defines the time after the idle timer expires during which the router
still considers a remote node on a DA circuit as "active." The
router can forward data on the DA circuit until the reserve timer
expires.
- Idle Timer
- Defines the length of time a DA adjacency my be idle (no data
transmission) before it is cleared.
- Max SVCs
- Defines the maximum number of SVC adjacencies supported by this DA
circuit. If no call can be placed because the maximum SVC adjacencies
has been reached, then an event "Exceed Max SVC adjacencies" is
generated.
- receive-password
- Adds an ASCII character string (16 characters maximum) that authenticates
all incoming packets. An incoming packet whose password matches one of
the set of receive-passwords is processed through the IS; any incoming
packets whose passwords do not match are dropped.
Example:
add receive-password
Note: | You get an error message if you use an invalid password
type.
|
Password type [Domain]:
Password [ ]:
Reenter password:
- Password type
- Designates one of the two types of passwords, domain or
area.
- Domain passwords are used with L2 LSPs (Level 2, Link State Packets) and
SNPs (Sequence Number PDU).
- Area passwords are used with L1 LSPs and SNPs.
- Password
- Designates the character string that you are using for
authentication. Maximum allowable string is 16 characters.
- template template-name routing-circuit-name destination-DTE
call-UserData
- Creates a template by which the router makes outgoing calls on a
static-out routing circuit. Templates for static-out circuits are
analogous to filters for static-in circuits.
The template-name is the name you give the template. The
routing-circuit-name is the name of the routing circuit with which
the template is associated.
The destination-DTE is an address for the remote router of up to
14 digits.
The call-UserData must match the call data set up for a filter
on the remote circuit. Call-UserData can have one of three
values - osi, dec, or user:
- For osi the router automatically configures an ISO protocol
discriminator for the call data and requires the call to go to an OSI
router.
- For dec the user data identifies the outgoing calls as coming
from a Digital Equipment Company router.
- For user you are prompted for an additional entry of up to 16
octets. Enter text to match the user data of the appropriate filter on
a remote router.
Example:
add template
Template Name []?
Routing Circuit Name []?
DTE Address []?
Call UserData (OSI/DEC/USER) ?
If you choose user this additional prompt appears:
(max 16 octets) [] ?
Enter up to 16 octets of text for user data.
Allows you to modify the parameters of ISO/DNV records created in the
permanent database.
Syntax:
- change
- filter
-
- prefix-address
-
- routing-circuit
-
- template
- filter filter-name
- Changes the values for routing circuit filter parameters. You can
enter a filter name or let the router prompt you for the filter name.
The values in brackets [] are the current values for the
parameters; the configured value read from the permanent database.
Example: change filter
Filter Name [currentvalue]?
DTE Address [currentvalue]?
Call Userdata (OSI/DEC/USER)? [currentvalue]?
If you select user, this additional prompt appears for you to
enter user data; followed by a Priority prompt:
(max 16 octets) [currentvalue] ?
- prefix-address
- Changes the address data for subnets. The router prompts you for
the address data.
Example: change
prefix-address
LAN Subnet:
Interface Number [0]:
Address Prefix [ ]:
MAC Address [ ]:
Default Metric [20]:
Metric Type [Internal]:
State [ON]?
X.25 Subnet:
Interface Number [0]:
Address Prefix [ ]:
Mapping Type [Manual]:
DTE Address [ ]:
Default Metric [20]:
Metric Type [Internal]:
State [ON]?
Frame Relay Subnet:
Interface Number [0]:
Address Prefix [ ]:
DTE Address [ ]:
Default Metric [20]:
Metric Type [Internal]:
State [ON]?
- Interface Number
- Indicates the interface over which the address is reached.
- Address Prefix
- Indicates the destination NSAP prefix (20 bytes maximum).
- MAC Address
- Indicates the destination MAC address. You must specify this
address if the interface corresponds to a LAN subnet. This prompt will
only appear if the interface is connected to a LAN subnet.
- Mapping Type
- Indicates how the destination physical address is determined,
manual or X.121.
- If manual, the protocol prompts you for the DTE address.
- If X.121, the protocol will not prompt you for the DTE
address. The DTE address in this instance is extracted from the
NSAP.
- DTE Address
- Defines the destination DTE address. You must specify this address
if the interface is X.25 and the mapping type is manual. This
prompt only appears if the interface is configured for X.25 and the
mapping type is manual.
- Default Metric
- Indicates the cost of the address.
- Metric Type
- Indicates whether the metric cost is used for external (E) routing or
internal (I) routing.
- State
- When set to ON, this address will receive packets. When set to OFF,
this is a non-functional address.
- routing-circuit routingcircuitname
- Changes the values of the configuration for a routing circuit. You
can enter a routing circuit name or let the router prompt you for a
name. The values in brackets [] are the current values taken
from the permanent database.
Example: change routing-circuit
Routing Circuit Name [currentvalue]?
Recall Timer (0-65535) [currentvalue]?
Max Call Attempts (0-255) [currentvalue]?
Initial Min Timer (1-65535) [currentvalue]?
Enable ES-IS [currentvalue]?
Enable IS-IS [currentvalue]?
Level 2 only [currentvalue]?
External Domain [currentvalue]?
Default Metric [currentvalue]?
ESIS IS Hello Timer [currentvalue]?
ISIS Hello Timer [currentvalue]?
Enable DECnetV Link Initialization [currentvalue]?
Modify Receive Verifier (YES/NO) [currentvalue]?
Modify Transmit Verifier (YES/NO) [currentvalue]?
Explicit Receive Verification (TRUE/FALSE) [currentvalue]?
- template template-name
- Changes the values of the template for a static-out routing
circuits. You can enter a template name or let the router prompt you
for a template name. The values in brackets [] are the
current values for the parameters; the configured values read from the
permanent database.
Example: change template
Template Name [currentvalue]?
DTE Address [currentvalue]?
Call UserData (OSI/DEC/USER)? [currentvalue]
If you select user, this additional prompt appears for you to
enter your user data; followed by a Priority prompt:
(max 16 octets) [currentvalue] ?
Priority (1-10) [currentvalue]?
Use the clear command to erase SRAM or to remove the receive or transmit
password.
Syntax:
- clear
- receive-password
-
- sram
-
- transmit-password
- receive-password
- Removes all of the receive-passwords previously configured using
the add receive-password command.
Note: | You will receive an error message if you use an invalid password type.
|
- Example:
- clear receive
Password Type [Domain]:
- Password Type
- Specifies the type of password being used, Domain or
Area. Refer to the
add receive-password command for description of these
passwords.
- SRAM
-
Use this parameter to erase the OSI configuration from SRAM.
Attention: Use this command only if you intend to
erase the configuration.
Example:
clear sram
Warning: All OSI SRAM Information will be erased.
Do you want to continue? (Y/N) [N]?
- Transmit-password
- Removes the transmit-password previously configured using the
set transmit-password command. The output for
this parameter is the same as that of the receive-password
parameter.
Note: | You will receive an error message if you use an invalid password type.
|
Example:
clear password transmit
Password Type [Domain]:
Use the delete command to remove parameters previously
configured using the set or add command.
Syntax:
- delete
- adjacency
-
- alias
-
- area
-
- filter (DEC configuration only)
-
- prefix-address
-
- routing-circuit
-
- subnet
-
- template (DEC configuration only)
-
- virtual-circuit
- adjacency
- Removes a statically configured ES adjacency previously configured with
the set adjacency command.
Example:
delete adjacency
Interface Number [0]?
Area Address [ ]?
System ID [ ]?
- Interface number
- Indicates the interface of the adjacency.
- Area address
- Indicates the area address of the adjacency.
- System ID
- Indicates the portion of the NET that identifies the adjacency within the
area.
- alias
- Removes the ASCII string that designates a portion of an area address or
system ID.
- Example:
-
delete alias
ALIAS [ ]?
- area address
- Removes the area address (address) previously configured with
the add area command.
Example:
delete area 47000580999999000012341234
- filter filter-name
- Removes a filter record from the permanent database.
Example:
delete p_systems
- prefix-address
- Removes the prefix-address previously configured with the
set prefix-address command.
Example: delete
prefix-address
Interface Number [0]?
Address Prefix [ ]
- Interface number
- Indicates the interface number over which the prefix-address is
configured.
- Address Prefix
- Indicates the destination NSAP prefix.
- Interface number
- Indicates the interface number over which the PVC is configured.
- DTE address
- Indicates the DTE address of the X.25 network to which you are
connecting or the DLCI of Frame Relay network to which you are
connecting.
- routing-circuit routing-circuit-name
- Removes an X.25 routing circuit that was established with add
routing-circuit from the permanent database.
Example:
delete routing-circuit p_system2
- subnet intfc#
- Removes a subnet that was previously configured with the set
subnet command. Intfc# indicates the interface number
of the configured subnet.
Example:
delete subnet 1
- template template-name
- Removes the template for a static outgoing routing circuit by which the
router generates outgoing X.25 messages from the permanent
database.
Example:
delete template x25_5
- virtual-circuit
- Removes an X.25 or a Frame Relay virtual circuit that was
previously configured with the set virtual-circuit command.
Example:
delete virtual-circuit
Interface number [0]?
DTE address []?
- Interface number
- Interface number over which the virtual circuit is configured.
- DTE address
- DTE address of the X.25 network to which you are connecting or the
DLCI of Frame Relay network to which you are connecting.
Use the disable command to disable those features previously
enabled using the enable command.
Syntax:
- disable
- osi
-
- routing-circuit
-
- subnet
- osi
- Disables the OSI protocol on the router.
- routing-circuit routing-circuit-name
- Disables the specified routing circuit.
Use the add routing-circuit command to set up
routing-circuits.
- subnet interface#
- Disables the OSI protocol on the specified subnet
(interface#).
Example:
disable subnet 0
Use the enable command to enable the OSI protocol or an OSI
subnet.
Syntax:
- enable
- osi
-
- routing-circuit...
-
- subnet...
- osi
- Enables the OSI protocol on the router.
- routing-circuit routing-circuit-name
- Enables the specified routing circuit.
Use the add routing-circuit command to set up
routing-circuits.
Example:
enable routing-circuit p_system2
- subnet interface#
- Enables the OSI protocol on the specified subnet
(interface#).
Example:
enable subnet 0
Use the list command to display the current configuration of the OSI
protocol.
Syntax:
- list
- adjacencies
-
- algorithm
-
- alias
-
- filter (DEC configuration only)
-
- globals
-
- password
-
- phaseivpfx
-
- prefix-address
-
- routing-circuits (DEC configuration only)
-
- subnets
-
- templates (DEC configuration only)
-
- timers
-
- virtual-circuits
- adjacencies
- Displays all statically configured ES adjacencies.
Example:
list adjacencies
Ifc Area Address System ID MAC Address
0 0001-0203-0405 0001-0203-0405
1 0002-4000-0000 0000-0019-3004
- Ifc
- Indicates the interface number that connects to the adjacency.
- Area Address
- Indicates the area address of this ES adjacency.
- System ID
- Indicates the portion of the NET that identifies the adjacency.
- MAC Address
- Indicates the MAC address (SNPA) of the adjacency.
- algorithm
- Displays the routing algorithm that is configured in SRAM for the DNA V
protocol. If you are running the OSI protocol only, this parameter is
unsupported.
Example:
list algorithm
Level 1 algorithm LINK_STATE
Level 2 algorithm DISTANCE_VECTOR
- Level 1 Algorithm
- Indicates the current configuration of the routing algorithm for level 1,
Link State (default) or Distance Vector.
- Level 2 Algorithm
- Indicates the current configuration of the routing algorithm for level 2,
Link State or Distance Vector (default).
Note: | Depending on whether DNA IV is enabled or disabled, the routing algorithm
displayed here may be different from what is running on the router.
|
- alias
- Displays the configured aliases and their corresponding address
segments.
Example:
list aliases
Alias Segment Offset
joplin AA0004000104 1
moon 0000931004F0 1
trane 000093E0107A 1
- filter
- Displays the defined filters for X.25 circuits.
Example:
list filters
Rout Cir Name Filter Name DTE Addr Pri Call Data
routeCir2 filter1 25 5 81
- globals
- Displays the router's current NET, area addresses, switch settings,
global parameters, and timer configuration.
Example:
list globals
DNAV State: Enabled* Network Entity Title: 4700050001:0000931004F0
Manual Area Addresses:
1. 4700050001 2. 7700050011
Switches:
ESIS Checksum = On ESIS Init Option = Off
Authentication = Off
Globals:
IS Type = L2 System ID Length = 6
L1 LSP Size = 1492 bytes L2 LSP Size = 1492 bytes
Max IS Adjs = 50 Max ES Adjs = 200
Max Areas = 50 Max ESs per Area = 50
Max Ifc Prefix Adds = 100 Max Ext Prefix Adds = 100
Max Synonymous Areas = 3 Max Link State Updates = 100
- OSI State or DNAV State
- Indicates if the OSI or DNA V protocol is running on the router.
- Network Entity Title
- Indicates the area address and system ID that make up the router's
NET.
- Manual Area Addresses
- Areas that the router operates within. The first area address
reflects the router's configured NET area address. Additional area
addresses were added with the add area command.
- Globals:
- Indicates the currently configured global parameters:
- IS Type
- The router's designation in the OSI environment: L1 or
L2.
- Domain ID Length
- The size (in bytes) of the system ID portion of the NET.
Note: | All routers throughout the domain must agree on the length of the domain
ID.
|
- L1 LSP Size/L2 LSP Size
- Displays the L1 and L2 maximum LSP buffer size.
- Max IS Adjacencies/Max ES Adjacencies
- Displays the maximum number of ES and IS adjacencies that are allowed for
all circuits.
- Max Areas
- Displays the maximum number of areas in the routing domain.
- Max ESs per Area
- Displays the maximum number of ESs allowed in one area.
- Max Int Prefix Adds
- Displays the maximum number of internal prefix addresses.
- Max Ext Prefix Adds
- Displays the maximum number of external prefix addresses.
- Max Synonymous Areas
- Displays the maximum number of level 1 areas serviced by this
router.
- password
- Displays the number of transmit and receive passwords configured for each
OSI Domain and Area. You configure receive passwords using the add
receive-password command. You configure transmit passwords using
the set transmit-password command.
Example:
list password
Number of Passwords Configured:
-- Domain --
Transmit = 3
Receive = 2
-- Area --
Transmit = 4
Receive = 6
- phaseivpfx
- Displays the configured DNA phase IV address-prefix that the OSI protocol
is using to route packets to a connected DNA IV network.
Example:
list phaseivpfx
Local Phase IV Prefix: 49
- prefix-address
- Displays all the SNPAs for statically configured routes.
Example:
list prefix:-addresses
Ifc Type Metric State Address Prefix Dest Phys Address
0 INT 20 On 470006 302198112233
1 EXT 50 OFF 470006 302198223344
- Ifc
- Indicates the interface number where the address can be reached.
- Type
- Indicates the type of metric, either internal (INT) or external
(EXT).
- Metric
- Indicates the cost of the reachable address.
- Address prefix
- Indicates the destination NSAP prefix. This prefix may be 20 bytes
long.
- Dest Phys Address
- Indicates the destination DTE address if this interface is X.25 and
the configured mapping is manual.
- routing-circuits
- Displays a summary of all routing-circuits or details of each routing
circuit.
Example:
list routing circuits
Summary or Detailed [Summary]? Summary
Ifc Name Type Enabled
0 routecir1 STATIC-OUT YES
0 routecir2 STATIC-IN YES
0 routecir3 DA YES
Summary or Detailed [Summary]? Detailed
Routing Circuit Name [] routecir2
Interface #: 0
Enabled: YES
Type: STATIC
Direction: Incoming
Initial Minimum Timer: 55
Enable IS-IS: YES
L2 Only: NO
External Domain: NO
Metric: 20
IS-IS Hello Timer: 3
DECnetV Link Initialization: YES
Receive Verifier:
Transmit Verifier:
Explicit Receive Verification: TRUE
- Interface # / Ifc
- The logical X.25 interface for this routing-circuit.
- Name
- The alphanumeric name of this routing-circuit record.
- Enabled
- Indicates the state of the routing-circuit: YES for enabled, NO for
disabled.
- Type
- Indicates whether the circuit is STATIC-IN, STATIC-OUT, or DA (dynamically
allocated).
- Direction
- Indicates how the router establishes a static routing circuit: by an
incoming call request (IN) or an outgoing call request (OUT).
In either case, the SVC is initially established upon operator action, but
the circuit is not fully enabled until both ends of the circuit have
initialized successfully.
- Initial Min Timer
- The amount of time (in seconds) that a static-out circuit waits for a link
to be initialized (reception of either an ESH or an ISH) after the call
request has been accepted. If the initial min timer expires before the
link is fully initialized, the SVC is cleared and an event is generated
indicating initialization failure.
- Enable IS-IS
- Indicates whether the IS-IS protocol is enabled on this circuit.
- L2 Only
- Indicates whether this routing circuit is used for Level2 routing
only.
- External Domain
- Indicates whether the router transmits and receives messages to and from a
domain outside its IS-IS routing domain.
- Metric
- Gives the cost of this address.
- ISIS Hello Timer
- Gives the time interval between transmissions of ISIS hellos.
- DECnetV Link Initialization
- Indicates whether DEC-style link initialization for this circuit is
enabled (YES) or disabled (NO).
- Receive Verifier
- Displays verification data to be checked against a received XID when
verifying by circuit.
- Transmit Verifier
- Displays verification data to be included in XIDs when verifying by
circuit.
- Explicit Receive Verification
- Indicates whether verification is done by the circuit or the
system. TRUE indicates verification by the circuit, FALSE indicates
verification by the system.
- Subnet subnet.reprt intfc#
- Displays subnet information.
- Subnet.reprt has two options, Summary and
Detailed.
- Summary displays information for all configured subnets.
- Detailed displays information for LAN subnets only.
- Intfc# is the interface that connects to the subnet.
Example:
list subnet summary
Ifc State Type ESIS ISIS L2 Only Ext Dom Metric EIH (sec) IIH(sec)
0 On LAN Enb Enb False False 20 10 3
2 On X25
3 On Frl
- Ifc
- Indicates the interface number of the subnet.
- State
- Indicates the state of the interface, ON or OFF.
- Type
- Indicates the type of subnet: LAN, X25,
- ESIS
- Indicates the state of the ES-IS protocol, enabled (Enb) or
disabled (Dis).
- ISIS
- Indicates the state of the IS-IS protocol, enabled (Enb) or
disabled (Dis).
- L2 Only
- Indicates if the router is operating at level 2 only, yes (true) or no
(false).
- Ext Dom
- Indicates if the router is operating outside the IS-IS routing
domain (external domain).
- Metric
- Indicates the cost of using this subnet.
- EIH
- Indicates the interval at which ES hello messages are sent out over the
subnet.
- IIH
- Indicates the interval at which IS hello message are sent out over the
subnet.
Example:
list subnet detailed
Interface Number [0]? 0
Detailed information for subnet 0:
ISIS Level 1 Multicast: 018002B000014
ISIS Level 2 Multicast: 018002B000015
All ISs Multicast: 009002B000005
All ESs Multicast: 009002B000004
Level 1 Priority: 64
Level 2 Priority: 64
- ISIS Level 1 Multicast
- Indicates the multicast address to use when transmitting and receiving L1
IS-IS PDUs.
- ISIS Level 2 Multicast
- Indicates the multicast address to use when transmitting and receiving L2
IS-IS PDUs.
- All ISs Multicast
- Indicates the multicast address to use when receiving ES hellos.
- All ESs Multicast
- Indicates the multicast address to use when transmitting IS hellos.
- Level 1 Priority/Level 2 Priority
- Indicates the router's priority for becoming the designated router on
the LAN.
- templates
- Displays a list of templates defined on this router.
Example:
list template
Route Cir Name Template Name DTE Addr Call UserData
routetest2 temptest2 25 81
- timers
- Displays the OSI/DNA V timer configuration (what is running on the router,
OSI, or DNA V).
Example:
list timers
Timers:
Complete SNP (sec) = 10 Partial SNP (sec) = 2
Min LSP Gen (sec) = 30 Max LSP Gen (sec) = 900
Min LSP Xmt (sec) = 30 Min Br LSP Xmt (msec) = 33
Waiting Time (sec) = 60 DR ISIS Hello (sec) = 1
ES Config Timer (sec) = 10
- Timers:
- Indicates the configuration of the OSI timers excluding any per circuit
timers.
- Complete SNP
- The interval between generation of complete SNPs.
- Partial SNP
- The minimum interval between sending partial SNPs.
- Min LSP Generation/Max LSP Generation
- The minimum and maximum intervals between generations of LSPs.
- Min LSP Transmission
- The minimum interval between LSP retransmissions.
- Min Broadcast LSP Transmission
- The minimum interval between LSP retransmissions on a broadcast
circuit.
- Waiting Time
- The time the update process must delay before entering the ON
state.
- DR ISIS Hello
- The interval between generations of IS-IS hello PDUs if this router
is a designated router.
- ES Config Timer
- The minimum interval between that an ES must send a hello packet each time
an interface comes up.
- virtual-circuits
- Displays information about all X.25 virtual circuits.
Example: list virtual-circuits
Use the set command to configure the router to run the OSI
protocol.
Syntax:
- set
- adjacency
-
- algorithm
-
- globals
-
- network-entity-title
-
- phaseivpfx
-
- subnet
-
- switches
-
- timers
-
- transmit-password (DEC configuration only)
-
- virtual-circuit (IBM 2210 configuration only)
- adjacency
- Adds or changes an ES adjacency. Add an ES adjacency for all LAN
ESs that do not run the ES-IS protocol.
Example:
set adjacency
Interface Number [0]:
Area Address [ ]:
System ID [ ]:
MAC Address [ ]:
- Interface Number
- Indicates the interface number that connects to the adjacency.
- Area Address
- Indicates the area where the adjacency is located.
- System ID
- Indicates system ID portion of the NET that is used to identify the
adjacency.
- MAC Address
- Indicates the MAC address (SNPA) of the adjacency.
- algorithm
-
Note: | This is a DNA phase V command. This command will work only if the DNA
phase V protocol is included in the software load. This enables you to
select the type of routing algorithm that you are using for the DNA routing
protocol, link state (DNA V) or distance vector (DNA IV).
Example:
set algorithm
Level 1 Algorithm [link_state]?
Level 2 Algorithm [distance_vector]?
- Level 1 Algorithm
- Selects the type of routing algorithm, link_state (for DNA V networks) or
distance_vector (for DNA IV networks).
- Level 2 Algorithm
- Selects the type of routing algorithm, link_state (for DNA V networks) or
distance_vector (for DNA IV networks).
|
- globals
- Configures the global parameters required by the OSI protocol.
Example:
set globals
IS Type [L2]:
System ID Length [6 bytes]:
Max Synonymous Areas [3]:
L1 LSP Buffer Size :[1492 bytes]:
L2 LSP Buffer Size [1492 bytes]:
Max IS Adjacencies ]50[:
Max ES Adjacencies [200]:
Max Areas in Domain [50]:
Max ESs per Area [500]:
Max Internal Prefix Addresses [100]:
Max External Prefix Addresses [100]:
Max Link State Updates [100]?
- IS Type (L1 or L2)
- Selects the level of the router, level 1 or level 2.
- System ID Length
- Selects the length of the domain ID portion of the NET. This length
must be the same for all routers in same domain.
- Max Synonymous Areas
- Selects the maximum number of level 1 areas that are serviced by this
router.
- L1 LSP Buffer Size
- Selects the buffer size of the level 1 LSPs and SNPs originated by the
router. Range is 512 to 1492. If the interface packet size is
less than what you configured here, OSI will not run, and the router generates
the ELS message ISIS.053.
- L2 LSP Buffer
- Selects the buffer size of the level 2 LSPs and SNPs originated by the
router. Range is 512 to 1492. If the interface packet size is
less than what you configured here, OSI will not run, and the router generates
the ELS message ISIS.053.
- Max IS Adjacencies
- Selects the total number of IS adjacencies allowed for all
circuits. This number is used to size the IS adjacency free
pool.
- Max ES Adjacencies
- Selects the total number of ES adjacencies allowed for all
circuits. This number is used to size the ES adjacency free
pool.
- Max Areas in Domain
- Selects the total number of areas in the routing domain. This
number is used to size the L2 routing table.
- Max ESs per Area
- Selects the total number ESs in any one area. This number is used
to size the L1 routing table.
- Max Internal Reachable Addresses
- Selects the number you are using to size the internal metric routing
table.
- Max External Reachable Addresses
- Selects the number you are using to size the external metric routing
table.
- Max Link State Updates
- Selects the number you are using to size the link state database.
- network-entity-title
- Configures the router's NET. The NET consists of the
router's system ID and area address.
Example:
set network-entity-title
Area-address [ ]
System-ID [ ]:
- Area-address
- Indicates one of area address portion of the router's NET. It
is included as the first address in the router's set of manual area
addresses. Each area address may be a maximum of 19 bytes.
- System-ID
- Defines the portion of the NSAP that identifies this specific
router. The system ID can be a maximum of 19 bytes, but the length must
agree with the domain ID length that you configured with the set
globals command.
- phaseivpfx
- Configures the prefix-address to allow the OSI protocol to route
packets to the attached DNA IV network. The default is 49
(hexadecimal).
- Example:
- set phaseivpfx
Local Phase IV prefix [49]?
- subnet
- Adds or changes a subnet. This parameter prompts you for different
information depending on the type of subnet that your configuring:
X.25, or LAN.
Example:
X.25 subnet:
set subnet
Interface number [0]:
Interface Type [X25]:
LAN subnet:
Interface number [0]:
Interface Type [LAN]:
Enable ES-IS [N]?
Enable IS-IS [N]?
Level 2 Only [N]?
External Domain [N]?
Default Metric [20]:
ESIS IS Hello Timer [10 sec]:
ISIS Hello Timer [3 sec]:
Modify Transmit password [No]?
Modify the set of receive passwords [No]?
L1 Priority [64]:
L2 Priority [64]:
All ESs [0x09002B000004]:
All ISs [0x09002B000005]:
All L1 ISs [0x0180C2000014]:
All L2 ISs [0x0180C2000015]:
Frame Relay subnet:
Interface number [0]:
Interface Type [FRL]:
- Interface number
- Binds the subnet to the specified interface.
- Enable ES-IS
- Indicates whether the ES-IS protocol is going to run over the
interface, yes (Y) or no (N).
- Enable IS-IS
- Indicates whether the IS-IS protocol is going to run over the
interface, yes (Y) or no (N).
- Interface Type
- Indicates the type of subnet: LAN, X.25, and Frame Relay
(FRL). LAN includes Ethernet and Token-Ring.
- Level 2 Only
- Indicates whether the subnet should run at level 2 only, yes (Y) or no
(N). A no designation allows the router to route over that subnet at
both level 1 and level 2.
- External Domain
- Indicates whether the circuit is operating outside the IS-IS
routing domain.
- Default Metric
- Indicates the cost of the subnet. Cost range 20-63.
- IS Hello Timer
- Indicates the period between transmissions of IS hello PDUs.
- ISIS Hello Timer
- Indicates the period between transmissions of L1 and L2 IS-IS hello
PDUs.
- Modify Transmit password
- Removes or changes a circuit transmit password. When you select
yes, this option prompts you with the following:
Delete or change the transmit password
[change]?
- Modify the set of receive passwords
- Removes all or adds one circuit receive-password. When you
select yes, this option prompts you with the following:
Delete all or add 1 receive password
[add]?
- L1 Priority/L2 Priority
- Indicates the router priority for becoming the designated router on the
LAN.
- All ESs
- Indicates the multicast address to use when transmitting IS hellos.
The default address reflects the ethernet/802.3 multicast
address. If you are connecting to a 802.5 LAN, use
C00000004000.
- All ISs
- Indicates the multicast address to use when receiving ES hellos.
The default address reflects the ethernet/802.3 multicast
address. If you are connecting to a 802.5 LAN, use
C00000008000.
- All L1 ISs
- Indicates the multicast address to use when transmitting and receiving L1
IS-IS PDUs. The default address reflects the
ethernet/802.3 multicast address. If you are connecting to a
802.5 LAN, use C00000008000.
- All L2 ISs
- Indicates the multicast address to use when transmitting and receiving L2
IS-IS PDUs. The default address reflects the
ethernet/802.3 multicast address. If you are connecting to a
802.5 LAN, use C00000008000.
- switches
- Turns the OSI options on or off.
Example:
set switches
ES-IS Checksum Option [OFF]?
ES-IS Init Option [OFF]?
ISIS Authentication [OFF]?
- IS-IS Checksum Option
- When switched on, the router generates checksums for all sourced
ES-IS packets.
- ES-IS Init Option
- When switched on, the router sends a directed IS Hello to a new ES
neighbor.
- IS-IS Authentication
- If switched on, each IS-IS packet includes the transmit password
configured for the domain, area, and circuits. Also, no checking
against receive passwords is done.
- timers
- Configures the OSI timers, excluding any circuit timers.
Example:
set timers
Complete SNP [10 sec]:
Partial SNP [2 sec]:
Minimum LSP Generation [30 sec]:
Maximum LSP Generation [900 sec]:
Minimum LSP Transmission [5 sec]:
Minimum Broadcast LSP Transmission [33 msec]:
Waiting Time [60 sec]:
Designated Router ISIS Hello [1 sec]:
Suggested ES Configuration Timer (sec) [10]:
- Complete SNP
- Selects the interval between the generation of complete sequence number
PDUs (SNP) by the designated router on a broadcast circuit.
- Partial SNP
- Selects the minimum interval between sending partial sequence number PDUs
(SNP).
- Minimum LSP Generation
- Selects the minimum interval between successive generations of Link State
Packets (LSPs) with the same LSP ID generated by the router.
- Maximum LSP Generation
- Selects the maximum interval between LSPs generated by the router.
- Minimum LSP Transmission
- Selects the minimum interval between retransmissions of a LSP.
- Minimum Broadcast LSP Transmission
- Selects the minimum transmission, in milliseconds, between transmission of
LSPs on a broadcast circuit.
- Waiting Time
- Selects the number of seconds the update process should delay in the
waiting state before entering the ON state.
- Designated Router ISIS Hello
- Selects the interval between the generation of IS-IS hello PDUs by
the router if the router is the designated router on a LAN.
- Suggested ES Configuration Timer
- Sets the option field of the IS hello message that instructs the ES to
change the rate at which it sends ES hellos.
- transmit-password
- Sets or changes a transmit password.
Example:
set transmit-password
Password type [Domain]:
Password [ ]:
Reenter password:
- Password type
- Selects the type of password: domain or
area.
- Domain passwords are used with L2 LSPs and SNPs. Area passwords are
used with L1 LSPs and SNPs.
- Password
- Indicates the character string that your using for authentication.
Maximum allowable string can be 16 characters.
- virtual-circuit
- Configures an X.25 SVC or PVC, or a Frame Relay PVC.
Example:
set virtual-circuit
Interface Number [0]:
DTE Address []:
Enable ISIS (Y or N) [Y]?
L2 only (Y or N) [N]?
External Domain (Y or N) [N]?
Default Metric [20]:;
ISIS Hello Timer [3 sec]?
Modify transmit password (y or n) [N]?
Modify the set of receive passwords [No]?
- Interface Number
- Indicates the X.25 or Frame Relay interface over which the virtual
circuit is configured.
- DTE Address
- Indicates the destination DTE address for X.25 or the DLCI (Data
Link Control Identifier) for Frame Relay. This address must be the same
as the one defined for the virtual circuit in the X.25 configuration or
the Frame Relay configuration.
- Default Metric
- Indicates the cost of the circuit.
- Enable IS-IS
- Indicates whether the IS-IS protocol is going to run over the
interface, yes (Y) or no (N).
- L2 only
- Indicates whether the circuit should run at level 2 only, yes (Y) or no
(N). A no designation allows the router to route at both level 1 and
level 2.
- External Domain
- Indicates whether the circuit is operating outside the IS-IS
routing domain.
For information on how to access the OSI/DECnet V
monitoring environment, refer to Getting Started (Introduction
to the User Interface) in the Software User's Guide
This section describes the OSI/DECnet V Monitoring commands. Use
these commands to gather information from the database.
The monitoring commands either display or modify the volatile
database.
Table 108. OSI/DECnet V Monitoring Commands Summary
Command
| Function
|
? (Help)
| Displays all the commands available for this command level or lists the
options for specific commands (if available). See "Getting Help".
|
Addresses
| Displays the router's NET and area addresses.
|
Change Metric
| Modifies the cost of a circuit.
|
CLNP-Stats
| Displays OSI CLNP statistics.
|
DNAV-info
| Displays the DNAV Level1 and Level2 routing algorithm currently in
effect.
|
Designated-router
| Displays the designated router for the LAN.
|
ES-adjacencies
| Displays all the ES adjacencies in the adjacency
database.
|
ES-IS-Stats
| Displays statistics associated with the ESIS protocol.
|
IS-adjacencies
| Displays all the IS adjacencies in the adjacency
database.
|
IS-IS-Stats
| Displays statistics associated with the ISIS protocol.
|
L1-routes
| Displays all the L1 routes in the Level 1 database.
|
L2-route
| Displays all the L2 routes in the Level 2 database.
|
L1-summary
| Displays a summary of the level 1 link state database.
|
L2-summary
| Displays a summary of the level 2 link state database.
|
L1-update
| Displays the information contained in L1 link state update
packet.
|
L2-update
| Displays the information contained in L2 link state update
packet.
|
Ping-1139
| Causes the router to send an echo request to a destination and wait
for a reply.
|
Route
| Displays the route a packet takes to a specified
destination.
|
Send echo packet
| Encodes an echo request message in the CLNP packet.
|
Show routing circuits
| Displays the state of user-defined routing circuits for the
specified interface. Applies when the router is configured as a
DEC-style router.
|
Subnets
| Displays all user-defined subnets.
|
Toggle
| Enables or disables the NSAP alias substitution
function.
|
Traceroute
| Displays the route a packet travels to its destination.
|
Virtual-circuits
| Displays all user-defined virtual circuits. Applies when the
router is configured as an IBM 2210-style router.
|
Exit
| Returns you to the previous command level. See "Exiting a Lower Level Environment".
|
Use the addresses command to list the router's NET and the
area addresses configured for this router.
Syntax:
- addresses
-
Example:
addresses
Network Entity Title:
4700-0500-01 000-9310-04F0
Area Addresses:
4700-0500-01
4900-02
- Network Entity Title
- Identifies the router. The NET consists of an area address and a
system ID.
- Area Address
- Indicates addresses within the routing domain. The router can have
a maximum of three area addresses configured at any one time.
Use the change metric command to modify the cost of a
circuit.
Syntax:
- change metric
-
Example:
change metric
Circuit [0]?
New Cost [0]?
- Circuit
- Indicates the circuit number that you want to change.
- New Cost
- Indicates the new cost of the circuit. Range: 1 to 63.
Use the clnp-stats command to display the OSI Connectionless
Layer Network Protocol (CLNP) statistics.
Syntax:
- clnp-statistics
-
Example:
clnp-statistics
Received incomplete packet 0
Received packet with bad NSAP length 0
Received packet with bad checksum 0
Received packet with bad version number 0
Received packet with bad type 0
Received packet with expired lifetime 0
Received packet with bad option 0
Received packet with unknown destination 0
Received packet with no segmentation permitted 0
Received data packet cannot be forwarded 0
CLNP input queue overflow 0
No buffer available to send error packet 0
No route to send error packet 0
Received OK CLNP packet 0
Cannot forward error packet 0
IS0 unknown initial protocol ID 0
Received error packet 0
Received local data packet 0
Sent error packet 0
received echo packet - destination unknown 0
cannot send an echo packet, handler error 0
sent ECHO reply packet 0
sent ECHO request packet 0
received ECHO Request 0
received ECHO reply 0
Error PDU dropped - SP, MS or E/R flag set 0
- Received incomplete packet
- Indicates that a data packet fragment recognized as an ISO CLNP data
packet was received.
- Received packet with bad NSAP length
- Indicates that an ISO CLNP data packet was received with an incorrect NSAP
length.
- Received packet with bad checksum
- Indicates that an ISO CLNP data packet was received with a bad
checksum.
- Received packet with bad version number
- Indicates that an ISO CLNP data packet was received with an incorrect or
unsupported version number.
- Received packet with bad type
- Indicates that an ISO CLNP data packet was received with an incorrect or
unsupported type field.
- Received packet with expired lifetime
- Indicates that an ISO CLNP data packet was received with an expired
lifetime.
- Received packet with bad option
- Indicates that an ISO CLNP data packet was received with a bad optional
parameter.
- Received packet with unknown destination
- Indicates that an ISO CLNP data packet was received but could not be
routed. The routing table contains no entry for the destination.
- Received packet with no segmentation permitted
- Indicates that an ISO CLNP data packet was received that needed
segmentation. The segmentation permitted flag was not set.
- Received data packet cannot be forwarded
- Indicates that an ISO CLNP data packet was received but could not be
routed because of a handler error.
- No buffer available to send error packet
- An attempt to send an ISO CLNP error packet failed because of a lack of
system I/O buffers.
- No route to send error packet
- An attempt to send an ISO CLNP error packet failed because it could not be
routed.
- Received OK CLNP packet
- Indicates that an ISO CLNP data packet was received and passed error
checking.
- Cannot forward error packet
- Indicates that an ISO CLNP error packet could not be routed because of a
handler error.
- ISO unknown initial protocol ID
- Indicates that an ISO CLNP packet was received with an unknown or
unsupported initial protocol identifier.
- Received error packet
- Indicates that an ISO CLNP error packet was received for this
router.
- Received local data packet
- Indicates that an ISO CLNP data packet was received with the destination
NSAP indicating one of the router's NSAPs.
- Sent error packet
- Indicates that ISO CLNP error packet was sent on receipt of a bad
packet.
Use the designated-router command to display the designated
router for the LAN subnets that are physically attached to this router and
actively running IS-IS.
Syntax:
- designated-router
-
Example:
designated-router
Designated Router Information:
Hdw Int# Circ L1DR L2DR
Eth/1 1 2 0000931004F002 0000931004F002
TKR/0 0 1 Elvis-01 Elvis-01
- Hdw
- Indicates the type and instance of LAN attached to this router.
- Int#
- Indicates the interface number of this router that attaches to the
LAN.
- Circ
- Indicates the circuit number assigned by the router. This number is
always one more than the interface number for LAN subnets.
- L1DR
- Indicates the LAN ID of the designated router. If the use of an
alias is enabled, this command displays the alias of the particular
segment. The LAN ID is the designated router's system ID
concatenated with a 1-byte locally-assigned circuit ID.
- L2DR
- Description is the same as L1DR described above.
Note: | If the designated router has not been elected yet, "Not Elected" will
be displayed instead of a LAN ID.
|
Use the dnav-info command to display the routing algorithm that
is currently running on the router.
Syntax:
- dnav-info
-
Example:
dnav-info
DNA V Level 1 Routing Algorithm: Distance-vector
DNA V Level 2 Routing algorithm: Distance-vector
Note: | Depending on whether or not DNA IV is enabled or disabled, the routing
algorithm displayed here may differ from what is configured in memory using
the set algorithm command at the OSI/DECnet V config>
prompt.
|
If DNA IV is enabled - the routing algorithm is the one configured in
memory.
If DNA IV is disabled - the routing algorithm is set to link state and may
differ from that set in memory.
Use the es-adjacencies command to display all the End System
(ES) adjacencies that are either configured or learned through the ESIS
protocol.
Syntax:
- es-adjacencies
-
Example:
es-adjacencies
End System Adjacencies
System ID MAC Address Interface Lifetime Type
6666-6666-6666 1234-FEAA-041C 0 50 DNAIV
- System ID
- The system ID of the ES adjacency.
- MAC Address
- Indicates the MAC address of the ES on the subnet.
- Interface
- Indicates the router's interface number where the ES adjacency was
learned.
- Lifetime
- Indicates the amount of time, in seconds, that the router has left before
the information received in the last ES Hello message is discarded. In
the case of static or a manually configured ES-Adjacency, this field reads
Static.
- Type
- Indicates the type of ES adjacency, OSI, DNAIV, DNAIV', and MANUAL
for statically configured adjacencies.
Use the es-is-stats command to display the statistics for the
ESIS protocol.
Syntax:
- es-is-stats
-
Example:
es-is-stats
ESIS input queue overflow 0
Received incomplete packet 0
Received packet with bad checksum 0
Received packet with bad version 0
Received packet with bad type 0
No iob available to send hello 0
Cannot send hello due to packet handler error 0
Sent hello 3672
Received packet with bad header 0
Received hello with bad nsap 0
Received hello packet with bad option 0
Received hello 0
Received hello with unsupported domain source 0
No resources to install route 0
Received hello with conflicting route 0
Timed out route reactivated 0
No resources to send redirect 0
Redirect not sent - handler error 0
Sent redirect 0
Timed out route 0
Timed out route 0
Unable to allocate resources for a new ES adjacency 0
hello PDU dropped, received over point-to-point circ 0
ESIS hello PPDU dropped, no matching area address 0
dropped hello packet - manual ES adjacency exists 0
- ESIS input queue overflow
- The ESIS packet was dropped because of a task input queue has
overflowed.
- Received incomplete packet
- A packet fragment recognized as an ESIS packet was received.
- Received packet with bad checksum
- An ESIS packet with a bad checksum was received.
- Received packet with bad version
- An ESIS packet with a bad or unsupported version was received.
- Received packet with bad type
- An ESIS packet with a bad or unsupported type field was received.
- No iob available to send hello
- An attempt to send an ESIS hello failed because of a lack of system I/O
buffers.
- Cannot send hello due to packet handler error
- An ESIS hello could not be sent because of a handler error.
- Sent hello
- An ESIS hello was sent out an interface.
- Received packet with bad header
- An ESIS hello packet with a bad holding time or received field was
received.
- Received hello with nsap
- An ESIS hello packet with a bad NSAP or an NSAP that over ran the field
was received.
- Received hello packet with bad option
- An ESIS CLNP data packet was received with a bad option parameter.
- Received hello
- An ESIS hello packet was received on the interface.
- Received hello with unsupported domain source
- An ESIS hello packet was received from an unspecified domain
source.
- No resources to install route
- An ESIS hello packet was received, but there were no resources to install
the route.
- Received hello with conflicting route
- An ESIS hello packet was received but could not be entered into the
database. A previously-defined static or dynamic route in the database
conflicts with the route in the hello.
- Timed out route reactivated
- An ESIS hello packet with a previously timed out route was
received.
- No resources to send redirect
- An ESIS redirect packet could not sent because of a lack of
resources.
- Redirect not sent handler error
- An ESIS redirect packet could not be sent because of a handler
error.
- Sent redirect
- An ESIS redirect packet was sent out the interface.
- Timed out route
- An ESIS hello route has timed out.
- Unable to allocate resources for a new ES adjacency
- An ES-IS hello packet was received but the router had insufficient
resources to establish an ES adjacency with the sending node.
- hello PDU dropped, received over point-to-point circ
- An ES-IS hello packet was dropped because the circuit involved is a
point-to-point circuit.
- ESIS hello PPDU dropped, no matching area address
- An ES-IS hello packet was dropped because the area did not match the
router's area address. The ES-IS protocol applies to one area
only.
- dropped hello packet-manual ES adjacency exists.
- An ES-IS hello packet was dropped because a static ES adjacency exists
with the sending node.
Use the IS-adjacencies command to list all the IS adjacencies
that are learned through the ISIS protocol.
Syntax:
- is-adjacencies
-
Example:
is-adjacencies
Intermediate System Adjacencies
System ID MAC Address Int Level Usage State Life Type
0000-9310-04C8 AA00-0400-EF04 0 L1 L1/L2 DOWN OSI
0000-9310-04C8 AA00-0400-EF04 0 L2 L1/L2 DOWN DNAIV
AA00-0400-0504 AA00-0400-0504 1 L2 L2 UP 5390 OSI
- System ID
- The system ID of the IS adjacency.
- MAC Address
- Indicates the MAC Address of the IS adjacency.
- Int
- Indicates the router's interface number that connects to the IS
adjacency.
- Level
- For LANs this indicates the neighbor system level from type of hello
message, L1 or L2. For point-to-point this indicates the neighbor
system type L1 only, otherwise L2.
- Usage
- Indicates from the hello packet circuit type, L1 only, L2 only, or L1 and
L2.
- State
- Indicates the operational state of the IS adjacency, up or down.
- Life
- Indicates the amount of time, in seconds, before discarding the last IS
Hello message.
- Type
- Indicates the routing protocol type of the IS adjacency, OSI or DNA
IV.
Use the is-is-stats command to display information associated
with the ISIS protocol.
Syntax:
- is-is-stats
-
Example:
is-is-stats
Link State Database Information
no. of level 1 LSPs 1 no. of level 2 LSPs 0
no. of L1 Dijkstra runs 21 no. of L2 Dijkstra runs 0
no. of L1 LSPs deleted 0 no. of L2 LSPs deleted 0
no. of routing table entries allocated 6
Packet Information
level 1 lan hellos rcvd 0 level 1 lan hellos sent 10967
level 2 lan hellos rcvd 0 level 2 lan hellos sent 10967
pnt to pnt hellos rcvd 0 pnt to pnt hellos sent 0
level 1 LSPs rcvd 0 level 1 LSPs sent 40
level 2 LSPs rcvd 0 level 2 LSPs sent 0
level 1 CSNPs rcvd 0 level 1 CSNPs sent 0
level 2 CSNPs rcvd 0 level 2 CSNPs sent 0
level 1 PSNPs rcvd 0 level 1 PSNPs sent 0
level 2 PSNPs rcvd 0 level 2 PSNPs sent 0
- no. of level 1/level 2 LSPs
- Indicates the number of L1 and L2 link state packets that are in the
database.
- no. of L1/L2 Dijkstra runs
- Indicates the number of times the router computed the L1 and L2 routing
tables.
- no. of L1/L2 LSPs deleted
- Indicates the number of L1 and L2 link state packets that were deleted
from the database.
- no. of routing table entries allocated
- Indicates the number of entries the routing able currently holds.
- level 1/level 2 lan hellos rcvd
- Indicates the number of LAN hellos the router has received.
- level 1/level 2 hellos sent
- Indicates the number of LAN hellos that router has sent.
- pnt to pnt hellos rcvd
- Indicates the number of point-to-point hellos that the router has
received.
- pnt to pnt hellos sent
- Indicates the number of point-to-point hellos that the router has
sent.
- level 1/level 2 LSPs rcvd
- Indicates the number of L1 and L2 link state packets (LSPs) that the
router has received.
- level 1/level 2 LSPs sent
- Indicates the number of L1 and L2 LSPs that the router has sent.
- level 1/level 2 CSNPs rcvd
- Indicates the number of L1 and L2 complete sequence number PDUs (CSNPs)
that the router has received.
- level 1/level 2 CSNPs sent
- Indicates the number of L1 and L2 CSNPs that the router has sent.
- level 1/level 2 PSNPs rcvd
- Indicates the number of L1 and L2 partial sequence number PDUs (PSNPs)
that the router has received.
- level 1/level 2 PSNPs sent
- Indicates the number of L1 and L2 PSNPs that the router has sent.
Use the l1-routes command to display all the level 1 routes that
are in the L1 routing database.
Syntax:
- l1-routes
-
Example:
l1-routes
Level 1 Routes
Destination System ID Cost Source Next Hop
0000-9300-0047 0 LOCArea *
AA00-0400-080C 1 ESIS AA00-0400-0C04, Ifc 7
7777-7777-7777 0 ISIS 3455-6537-2215
- Destination System ID
- Indicates the system ID of the destination host.
- Cost
- Indicates the cost of this route.
- Source
- Indicates the one of three sources where the router learned of the
route: LOCAREA, ESIS, or ISIS.
- Next Hop
- Indicates the next hop a packet would take on its route. An
asterisk (*) designation refers to the router itself as the packet's
destination. An address with an interface number is either the MAC
address of a directly connected ES, or the DTE address if the next hop is an
X.25 switch, or a DLCI if the next hop is Frame Relay switch. A
system ID (34555372215) refers to the next hop to destination.
Use the l2-routes command to display all the level 2 routes in
the L2 database.
Syntax:
- l2-routes
-
Example:
l2-routes
Level 2 Routes
Destination Cost Type Next Hop
4700-0500-01 0 LOC-AREA *
4900-02 20 AREA 0000-9310-04C9
- Destination
- Indicates the system ID of the destination area or reachable
address.
- Cost
- Indicates the cost of this route.
- Type
- Indicates the four types of routes: LOC-area (local), LOC-prefix,
area, prefix/I, and prefix/E. LOC-area is a directly connected
area; a LOC-prefix is a prefix that this router advertises; prefix/I
and prefix/E are routes that require another hop to reach their
destination.
- Next Hop
- Indicates the next hop a packet would take on its route. An *
designation, or a direct designation, refers to a directly-connected host off
the router. A system ID refers to the next router the packet must pass
through to reach its destination.
Use the l1-summary command to display a summary of the level 1
link state database.
Syntax:
- l1-summary
-
Example:
l1-summary
Link State Database Summary - Level One
LSP ID Lifetime Sequence # Checksum Flags Cost
0000-9300-40B0-0000 0 0 0 0 1024
0000-93E0-107A-0000 384 CE 3CC9 1 0
AA00-0400-0504-0000 298 8E 40F1 B 20
AA00-0400-0504-0100 4 B8 A812 3 20
Total Checksum 25CC
- LSP ID
- This represents the system ID of the source of the link state PDU plus two
additional bytes. The first additional byte designates the type of
update. 00 represents a non-psuedonode update. 01-FF
represents a pseudonode update for that circuit number. The second byte
represents the LSP number. This number is attached to the packet when
the data is contained in more than one packet.
- Lifetime
- Indicates the amount of time, in seconds, that router will maintain the
LSP.
- Sequence #
- Indicates the sequence number of the LSP.
- Checksum
- Indicates the checksum value of the LSP.
- Flags
- Indicates a one-octet value that reflects the flag field of the
LSP. The eight bits are broken down as follows:
- Bit 8
- Indicates the P flag. When set (1), the issuing IS supports the
optional Partition Repair function.
- Bits 7-4
- Indicate the ATT flag. When set (1), the issuing IS is attached to
other areas using one of the following: the Default Metric (bit 4), the
Delay Metric (bit 5), the Expense Metric (bit 6), or the Error Metric (bit
7).
- Bit 3
- Indicates the LSPDBOL flag. When set (1), an LSP database overload
has occurred. An LSP with this bit set is not used by the decision
process to calculate routes to another I through the originating
system.
- Bits 2-1
- Indicate the IS Type flag. When set to the following values,
designates the type of IS router, level 1 or level 2.
- Value
- Description
- 0
- Unused.
- 1
- Bit 1 set. Level 1 IS.
- 2
- Unused.
- 3
- Bits 1 and 2 set. Level 2 IS.
- Cost
- Indicates the cost of routing to that neighbor.
Use the l2-summary command to display a summary of the level 2
link state database.
Syntax:
- l2-summary
-
-
-
Example:
l2-summary
Link State Database Summary - Level Two
LSP ID Lifetime Sequence # Checksum Flags Cost
0000-9310-04F0-0000 33E 12 EF19 3 0
0000-5000-FB06-0000 455 4 2BB1 3 20
0000-5000-FB06-0100 469 12 DE32 3 20
Total Checksum 0
The description of the L2-summary output is the same as the l1-summary
command.
Use the l1-update command to display a link state update for the
specified level 1 IS.
Syntax:
- l1-update
-
Example:
l1-update
LSP ID []? 0000931004F0000
Link State Update For ID 0000931004F00000
Area Addresses
470005001
Intermediate System Neighbors Metric Two Way
0000931004F002 20 N
0000931004F001 20 Y
End System Neighbors Metric
00009310004F0 *
- LSP ID
- Indicates the system ID of the source of the link state PDU plus two
additional bytes. The first byte designates the type of update.
00 represents a non-pseudonode update. 01-FF represents a
pseudonode update. The second byte represents the LSP number.
This number is attached to the packet when the data is contained in more than
one packet.
- Area Addresses
- Indicates the area addresses in which this router is configured to route
packets.
- Intermediate System Neighbors
- Indicates adjacent neighbor ISs.
- Metric
- Indicates the cost to the neighbor IS.
- Two Way
- Indicates whether the router is receiving updates from its
neighbor.
- End System Neighbors
- Indicates any directly connected ESs.
Use the l2-update command to display the link state update for
the specified level 2 IS.
Syntax:
- l2-update
-
Example:
l2-update
LSP ID []? 0000931004F0000
Link State Update For ID 0000931004F00000
INTERMEDIATE SYSTEM NEIGHBORS METRIC TWO WAY
0000931004F002 20 N
0000931004F001 20 N
55002000182000 20 N
- Intermediate System Neighbors
- Indicates other directly connected ISs.
- Metric
- Indicates the cost to the IS.
- Two Way
- Indicates whether the router is receiving updates from its
neighbor.
Causes the router to send an echo request to a destination and wait for a
reply, as recommended in RFC 1139. RFC 1139 specifies this as an OSI
function and not as a DECnet function. Ping-1139 supports
short- and long-term echos. Short-term echos use regular CLNP data
packets, which makes them transparent to intermediate systems that do not
support RFC1139. Long-term echos use PING request/reply packets.
The default data length of the echo request packet is 16 bytes. You
can set the data length up to 64 bytes.
Once you enter the ping-1139 command, echo requests are sent
continually until you press any key. At that time, statistics are
displayed showing the number of requests transmitted and the number of replies
received.
Syntax:
- ping-1139
-
Example:
ping-1139
Long-term/Short-term [LONG-TERM]?
Destination NSAP: []? AA0003000A14
Data Length [16]?
PINGing AA0003000A14
---- PING Statistics ----
8 requests transmitted, 8 replies received
Use the route command to display the next hop a packet would
take to a specified destination (destnsap).
Syntax:
- route dest-nsap
-
Example:
route 490002aa0004000e08
Destination System: 0000-9310-04C9
Destination MAC Address: AA00-0400-1408
Interface: 0
- Destination System
- Indicates the system ID of the next hop IS. For a directly
connected ES, this will be blank.
- Destination MAC Address
- Indicates the MAC address of the next hop IS or the directly-connected
ES.
- Interface
- Indicates the interface that a packet would go out over to reach the next
hop IS or the directly-connected ES.
Use the send echo packet command to encode an echo request
message in the CLNP packet to the specified destination nsap. During
this command, the system does not interact with the OSI monitoring. To
verify that the echo request was sent and that an echo reply was received,
check the ELS (Event Logging System).
Note: | You cannot send an echo packet to yourself. If you try, you will
receive an CLNP.004 ELS message.
|
Syntax:
- send
-
Example:
send
Destination NSAP: []?
Use the subnets command to display information on all
operational subnets. Subnets that are down or disabled will not be
listed.
Syntax:
- subnets
-
Example:
subnets
L2
Hdw Int # Circ Only ES-IS IS-IS L1DR L1Pri L2DR L2pri Cost Ext
PPP/2 2 3 N N Y
Eth/0 0 1 N Y Y Y 64 N 64 20 N
- Hdw
- The type and instance of the network that connects to the subnet.
- Int #
- The router's interface number that connects to the subnet.
- Circ
- The circuit assigned ID for the ISIS protocol.
- L2 only
- Whether this router is a level 2 router only, Y (yes) or N (no).
- ES-IS
- The ES-IS protocol is enabled on the subnet, Y or N.
- IS-IS
- The IS-IS protocol is enabled on the subnet, Y or N.
- L1DR
- This router is the level 1 designated router for this subnet, Y or
N.
- L1Pri
- The subnet's level 1 priority for becoming the designated
router.
- L2DR
- This router is the level 2 designated router for this subnet, Y or
N.
- L2Pri
- The LAN subnet's level 2 priority for becoming the designated
router.
- Cost
- The cost of the circuit.
- Ext
- Whether the subnet is operating outside the IS-IS routing domain
(external).
Use the toggle alias/no alias command to enable or disable the
NSAP alias display function for the OSI protocol.
Syntax:
- toggle
-
Example:
toggle
Alias substitution is ON
Use the traceroute command to track the path an OSI packet takes
to a destination.
Note: | You cannot do a traceroute to yourself or you will receive the following
error message:
|
Sorry, can't traceroute to this router.
Syntax:
- traceroute address
-
Example:
traceroute 490002aa0004000e08
Successful trace:
TRACEROUTE 470007: 56 databytes
1 490002aa0004000e08 32ms 5ms 5ms
Destination unreachable response:
Destination unreachable
No response:
1 * * *
2 * * *
- TRACEROUTE
- Displays the destination area address and the size of the packet being
sent to that address.
- 1
- The first trace showing the destination's NSAP and the amount of time
it took the packet to arrive at the destination. The packet is traced
three times.
- Destination unreachable
- Indicates that no route to destination is available.
- 1 * * *
-
- 2 * * *
- Indicates that the router is expecting some form of response from the
destination, but the destination is not responding. The router will
wait 32 hops before timing out. Go to the ELS and turn on OSI CLNP
messages to determine why the host is not responding.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]